Skip to main content
London Borough of Hammersmith & Fulham

Brownfield land

There is a problem

  • 15 entries must have valid URIs

LBHF013

SiteReference
LBHF013
SiteNameAddress
111-115 Wandsworth Bridge Road
Deliverable
yes
HazardousSubstances
Hectares
0.03
MinNetDwellings
NetDwellingsRangeFrom
6
NetDwellingsRangeTo
6
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2018-01-03
PermissionType
full-planning-permission
PlanningHistory

PlanningHistory must be a real URL

PlanningStatus
permissioned
SiteplanURL
https://www.lbhf.gov.uk/sites/default/files/section_attachments/lbhf013_111-115_wandsworth_bridge_road.pdf
GeoX
POINT(-0.191518 51.473302)
GeoY
POINT(-0.191518 51.473302)
Notes
Some Amendement but no change. Site visit - difficult to dermine if the development has commenced. The LDD does not note it has started. Are conversions suitable for a brownfield register. I. Erection of a rear roof extension including the formation of a hip to gable roof extension; erection of rear extensions at first, second and third floor levels; alterations to front lightwell; excavation and enlargement of the existing basement and rear lightwell; erection of external staircases and roof terraces at the rear of the property; associated external alterations; conversion of the first, second and third floor levels into 3 x two bedroom and 3 x one bedroom self-contained flats.
OrganisationLabel
OrganisationURI
LastUpdatedDate
2019-11-30
FirstAddedDate
2018-12-31
EndDate

How to fix this issue

Your dataset is missing the PlanningHistory column.

The Brownfield land guidance explains how to fix the issue:

PlanningHistory

Enter links to any web pages that give information on the site’s planning history (include the “http://” or “https://” prefix). Fields in this column can contain more than one link, as long as you separate multiple links with the pipe character (‘|’). You can leave this field blank.

How to improve London Borough of Hammersmith & Fulham’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL